Miscellaneous Enhancements, Bug Fixes, and Expected Changes

Miscellaneous Enhancements

  • When downloading a Report Package, functions such as ReportWISetting(), ReportAsSoldSetting(), ReportWI(), and ReportNRI() now correctly read their values from the Report Favorite being used, rather than the user's current UI setting. This ensures each report in a package reflects the intended settings.
  • When deleting wells in Production History Management, a confirmation dialog is now presented, indicating how many wells will be permanently deleted before proceeding.
  • Support Admins and DB Admins can now view all documents under Enterprise > Documents, including non-public ones. A new Owner column is visible to these roles to identify who owns each non-public document.
  • The Help links on the CSV Import and Function Editor pages now point directly to the relevant documentation topics rather than the general help landing page.
  • When adding a row to a Report Package Download, an error message is now shown if no Report Favorites exist: "At least one Report Favorite must exist to add rows." Previously it wasn't clear why a row couldn't be added to the Report Package.
  • The Fit All v. Cum and Fit All v. Time buttons have been removed from the Production History decline curve editor, as curve fitting was unreliable for Flat and Linear curve types.
  • The project calculation duration (Calc For) is now stored at the project level rather than as a user preference, allowing each project to retain its own calculation horizon independently. A default value can be configured under Tools > Options and will be applied when creating new projects.

Miscellaneous Bug Fixes

  • Report averaging for user-defined average fields now produces correct totals when a report end date is specified.
  • Generating a project-level report using a Report Group no longer causes an error.
  • Grouped data in reports and graphs now correctly accounts for splits.
  • Shut-In Reports now display the correct halo range for each pair of wells, rather than always showing the Halo 0 range.
  • A crash that occurred when a Script Scenario name matched the name of an existing scenario has been resolved.
  • The WellList:Replace command is now available in Risk Scripting, where it was previously missing.
  • The Risk Scripting Reference window now opens correctly when clicking a command reference after changing the Script Name without first clicking elsewhere.
  • Gas composition changes now save correctly.
  • Multiple gas compositions are now calculated in the correct order. Previously, in certain cases, an incorrect composition was chosen based on the cumulative production.
  • Copying or deleting selected projects in the Project List now works correctly when a filter is active.
  • The Add Definition button on the User Defined Data (Company Level) page in the Administrator dropdown is no longer incorrectly disabled.
  • Function text is no longer corrupted when copied and pasted from Bulk Edit to Excel and back (the single quote prepended to functions is handled appropriately).
  • In particular report configurations, calculated incremental values are no longer incorrectly reported as zeros after calculation.
  • When a new well started mid-calculation and triggered a scheduler restart, a stale segment start date was retained, causing a spurious production spike in the affected well at that timestep.
  • Projects no longer unexpectedly change their schema version after importing data via the Val Nav plugin. This can still occur under certain circumstances, but the probability has been reduced.
  • Additional monitoring has been added to capture unexpected termination of sessions.
  • Copying a scenario via the Scenarios tab now correctly shows a warning when the copy fails due to the 10,000 asset limit.
  • A fix has been applied to the diamond removal algorithm used during network scheduling, which was producing incorrect results in certain topologies.
  • The list of Wells in the Network tab Asset Hierarchy now refreshes correctly after a well is successfully imported via CSV.

Expected Changes

  • Grouped data in reports now correctly accounts for splits. Grouped graphs and reports were displaying the full production from source wells without accounting for network splits, causing inflated values. Numbers in grouped report views will decrease for affected projects and now correctly reflect only the portion flowing to the selected asset.
  • Incremental values for certain facilities (specifically where roll-up numbers were correct but incrementals were zero) will now show correct non-zero values.
  • As noted in the solver section, projects using the "V3 Latest" setting will automatically use V3.2, which produces a more deterministic sort order during curtailment. This will cause small numerical differences in results output compared to the V3.1 solver.
  • When a new well started mid-calculation and triggered a scheduler restart, a stale segment start date was retained, causing a spurious production spike in the affected well at that timestep. Projects using the scheduler with multiple wells starting at different times may see smoothed production curves where a spike previously appeared.
  • Gas Compositions ordered by cumulative production were applied in the wrong sequence, and a related bug caused production to drop to zero when a composition change occurred. Any project using multiple time-stepped or cumulative-production-based gas compositions may see corrected composition values and potentially different volumetric results downstream.